home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-05
/
lanmodm1.zip
/
HELP.DOC
< prev
next >
Wrap
Text File
|
1990-06-01
|
8KB
|
199 lines
Cross Information Company
LAN+MODEM User Self-help Guide
May, 1990
This information has been prepared in an effort to help users locate
and correct problems with installation and usage of the software
included in the LAN+MODEM package.
In several places the term 'COMMnn' is used and refers to the network
name which the programs use. The 'nn' refers to a numeric designation
in the range '01' to '20' depending on the maximum drivers supported
by your package.
In what area are you having trouble?
Specific
1. NETDEV or UCOM can't locate MCOM driver name(s).
Go to section 1.1
General
2. MCOM
Go to section 2.1
3. NETDEV
Go to section 3.1
4. UCOM
Go to section 4.1
5. Third party INT14 Software
Go to section 5.1
1.1 When MCOM installs do you see the message 'now resident as
network name COMMnn'?
If No, go to section 2.1.
Make sure NETDEV or UCOM displays the message 'Calling COMMnn'
where nn is the same number as MCOM displays.
If No, change the '/START=' command for NETDEV or add 'COMMnn' to
the command line for UCOM.
If this message is followed by 'In Use' or 'Remote not listening'
or 'Timeout' then that particular MCOM driver is in use. Try
another.
Are you trying to connect over a bridge?
1. No
Go to section 100.
2. Yes
Go to section 1.1.2.
1.1.2 Using a bridge - What type of network are you on?
1. NetBIOS
If MCOM is on the other side of a bridge from NETDEV or UCOM,
then the bridge is not compatible or is not known to NetBIOS.
Check your LAN software installation. Generally if a server disk
can be shared on both sides of a bridge then LAN+MODEM should
work. If your bridged LANs are not sharing resources, try and
set them up so they do and try LAN+MODEM again. If they are, go
to section 100.
2. IPX
Check the documentation for the use of the NETEDIT utility. This
must be used whenever your network addresses are not 1, 2, or 3.
NETEDIT and IPXSTAT should both be moved from the UTIL
subdirectory to the directory where MCOM, UCOM, and NETDEV are
located; ignore the layout of the distribution diskette. Remove
all other copies of these files from the file server.
Cross Information Company
LAN+MODEM User Self-help Guide
May, 1990
Then use IPXSTAT and NETEDIT to properly code your network
addresses into the programs. Only when this is done should
copies of the programs be made for use on workstation boot disks
or other locations that will not read the programs updated on
the file server. If MCOM was run before these steps were taken,
reboot the respective machines with the updated copies of MCOM.
If you are still having problems, go to section 100.
2.1 Problems with MCOM
1. The problem is with initialization (when executing):
First of all you must know which serial port you wish to have
shared. If you are trying to use a port and MCOM says 'in use'
then there is another program which is using that port or IRQ.
Common conflicts include mouse, LAN, or FAX cards at IRQ4 or
IRQ3. Anytime another TSR is using a port, that port is
unavailable for use by LAN+MODEM. If MCOM says 'not found' then
the port could not be addressed at the standard address or IRQ
(interrupt request) for it.
The values MCOM uses are: Address (Hex) IRQ
COM1: 3F8 4
COM2: 2F8 3
COM3: 3E8 4
COM4: 2E8 3
Note that only two ports can be shared since only two IRQs can
be used on each computer.
Be sure to type 'MCOM 2' to use COM2 and skip COM1 when it is
used for another function.
If you have checked all these things and are still having
problems, go to section 100.
2. The problem is with operation (resident as TSR):
If the problem arises before a connection is attempted with
NETDEV or UCOM, make sure no other communications or serial
driver TSRs are attempting to use the same COM port as MCOM. If
not, go to section 100.
If the problem arises when running NETDEV or UCOM, see the
section appropriate for that program (3.1 or 4.1).
3.1 Problems with NETDEV
1. Not receiving any data?
You should use NETDEV, then (optional) NETDEV /START=nn, and
finally NETDEV /OPEN to open a channel to the MCOM driver. You
must get the message 'Available' before the channel is actually
opened.
If you see the message 'Available' when opening a NETDEV channel,
see section 4.1 for UCOM problems.
If not, see section 1 for connection problems.
4.1 Problems with UCOM
1. Not receiving any data? (cursor sits at Initializing Modem: )
If you are not using a modem on this channel (rare) then the
device or host you are connected to is probably off-line.
If you are using a modem, as you press any keys you should see
the TX indicator blinking on the right side of the status line.
You may need to adjust your monitor's contrast control.
If not blinking, go to section 100.
In the center of the status line should be the label 'COMMnn'
which indicates which MCOM driver to which you are connected. If
you see the word 'FLOW' instead then you are in a flow control
Cross Information Company
LAN+MODEM User Self-help Guide
May, 1990
'hold mode'. This should only be momentary. If it continues, it
means that the CTS signal into MCOM is being held 'off', which
indicates that your cable is missing the wire for this signal or
the device MCOM is connected to does not output a signal on this
wire. In the first case you will need a cable with control
signals RTS, CTS, DTS, DSR, CD, and RI connected. In the second
case, the device or cable will need to be changed so that CTS is
driven to the 'on' level.
(NETDEV only: use the utility program TERM.COM. If the label CTS
0 is shown for any length of time it indicates the flow control
'hold mode' problem as for UCOM in the previous paragraph).
If none of these problems are present, go to section 100.
5.1 Problems with third party INT14 software
1. Not receiving any data?
You should use NETDEV, then (optional) NETDEV /START=nn, and
finally NETDEV /OPEN to open a channel to the MCOM driver. You
must get the message 'Available' before the channel is actually
opened.
If you do not see the message 'Available' when opening a NETDEV
channel, see section 1 for connection problems.
Check the manual and the file README.DOC for any specific
instructions for using your package with LAN+MODEM. It must
specifically be written to use 'software interrupt' 14 to read
and write data. Some packages use only INT14 (eg. PROCOMM PLUS
Network Version) while others must be configured to use it (eg.
CROSSTALK Mk. 4). Check the manual for your package to make sure
it is configured for use with INT14.
If you are still having problems, see section 4.1 for UCOM
problems.
100. Unable to resolve problem using this guide
Try another modem and cable if possible. If this doesn't help,
Contact CIC for technical support. For data problems it is
generally better to have an external modem available for testing
since the status lights can be used to diagnose problems. Please
have your registration number (serial number) handy.
- end -